Deploy preview for carbon-elements ready!

Built with commit de479b1

https://deploy-preview-7729--carbon-elements.netlify.app

Deploy preview for carbon-components-react ready!

Built without sensitive environment variables with commit de479b1

https://deploy-preview-7729--carbon-components-react.netlify.app

@lee-chase thanks so much for putting this together! It's awesome to see the generation logic in there.

I'm a little hesitant about is adding this to the base packages, are there any other strategies we could use for enabling these kinds of transforms for adding classes to the paths?

One thing that came to mind is a dedicated package that uses the icon data from @carbon/icons and provides bespoke class names. It definitely isn't auto-generated, however, but may provide more control if that is needed.

@joshblack Another option would be to provide a wrapper to the Icon component, or perhaps just an alternate that walks the children and creates a component with classes added on the fly. The performance hit would be tiny on small SVGs.

Perhaps we can get together to discuss how #7751 / #7346 are progressed. Are there others you would suggest joining such a conversation @joshblack ?

@lee-chase I think moving forward @johnbister will be great on the design side.

On the technical side, I think it'd be great to have a dedicated package for this kind of stuff that uses the icon data from @carbon/icons to generate the icons with the preferred class names for the icons that are being worked on.

I think from that experiment we can get a feel for how widespread this use-case is and how folks will want to leverage it before folding it into @carbon/icons-react, if that makes sense.

Let me know what you think!

@lee-chase I think moving forward @johnbister will be great on the design side.

On the technical side, I think it'd be great to have a dedicated package for this kind of stuff that uses the icon data from @carbon/icons to generate the icons with the preferred class names for the icons that are being worked on.

I think from that experiment we can get a feel for how widespread this use-case is and how folks will want to leverage it before folding it into @carbon/icons-react, if that makes sense.

Let me know what you think!

Will try and sort this at some point Josh, but struggling for time.

Hey @lee-chase! 👋 Going to close this out since I think the group is going for a smaller approach first 👀 Let me know if this is not the case!

DCO Assistant Lite bot: Thanks for your submission! We ask that you sign our Developer Certificate of Origin before we can accept your contribution. You can sign the DCO by adding a comment below using this text:

I have read the DCO document and I hereby sign the DCO.

Lee Chase seems not to be a GitHub user. You need a GitHub account to be able to sign the DCO. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request}